chore: Bump the cloudhal group with 12 updates by dependabot[bot] · Pull Request #27 · cloudhal-dev/cloudhal.com

dependabot · 2026-11-11T03:08:24Z

Bumps the cloudhal group with 12 updates:

Package	From	To
@cloudhal/astro-renderer	`0.6.5`	`0.7.3`
@cloudhal/cli	`0.6.5`	`0.7.3`
@cloudhal/core-ts	`0.6.5`	`0.7.3`
@cloudhal/cloudflare	`0.6.5`	`0.7.3`
@cloudhal/agent-runtime	`0.6.5`	`0.7.3`
@cloudhal/analytics	`0.6.5`	`0.7.3`
@cloudhal/api	`0.6.5`	`0.7.3`
@cloudhal/comments	`0.6.5`	`0.7.3`
@cloudhal/core-contracts	`0.6.5`	`0.7.3`
@cloudhal/mcp-server	`0.6.5`	`0.7.3`
@cloudhal/schedules	`0.6.5`	`0.7.3`
@cloudhal/storage	`0.6.5`	`0.7.3`

Updates @cloudhal/astro-renderer from 0.6.5 to 0.7.3

Release notes

Sourced from @cloudhal/astro-renderer's releases.

Cloudhal 0.7.3

All @cloudhal/* packages and create-cloudhal at 0.7.3.

Changes

asset_refs is scoped by site (RFC-0045 §2.5, rollout step 0), and an unchanged import no longer rebuilds it (#196).

An import, push or pull planned unchanged used to rebuild the site's asset_refs from rows read at plan time. An edit that committed in between could lose its new row, so the asset it started using could be deleted and showed as unused. The rebuild now runs only in a batch that also writes the node set.

The rebuild records only references to assets of the same site, and splits its INSERT so each statement stays below 90 KB (large sites could exceed D1's statement limit). Its statements count against the import's 1,000-statement cap.

Deleting an asset and the media library's "unused" filter look only at references from the asset's own site, so a foreign archive naming another site's asset no longer blocks its delete or hides it.

A publish that changes an asset now also purges the pages that show it through a typed image or richText field (RFC-0041), not only through covers, bodies and sections.

While a field rename runs, entries not rewritten yet still hold the old key. Both the rebuild and the purge planner now read those entries through the definition's migration.fromKey, as the renderer does. An archive exported mid-rename keeps those entries' rows, and an asset change purges their pages.

Turkish: the strings added since the last review (the OAuth consent screen, Connected agents, the setup-link sign-up text, the Ended badge, the Build chat playground hint and the site status pages, #112) are reviewed and approved by the owner. 22 of 93 change: Connected agents says an agent "never" goes beyond your role again ("senin rolünü asla aşmaz"), "revoke" is "iptal et" as everywhere else, "operator" is "işletmeci" so it is not read as the Yönetici role, the setup-link text names the Sahip role, the consent title needs no suffix on the app's name, the invite page says "Çıkış yap" like its button, and the maintenance page says "Tahmini dönüş: {time}" and "Sabrınız için teşekkür ederiz".

Upgrade
npm install @cloudhal/[email protected] @cloudhal/[email protected] @cloudhal/[email protected] @cloudhal/[email protected]
npx cloudhal deploy
Docs: https://cloudhal.dev/docs/start/installation#upgrading

Cloudhal 0.7.2

All @cloudhal/* packages and create-cloudhal at 0.7.2.

Changes

A self-hosted site rebuilds itself on publish (#150). With CLOUDHAL_SITE_BUILD=on, which is the Docker image's default, cloudhal studio runs the image's site-build in a child process after every publish: a publish in Studio or through MCP, an approval, a rollback, or a release that goes live (at its time or through "Publish now"). It also runs it once at start.

One build per burst. A burst of publishes builds once (3 seconds after the last one, at most a minute after the first).

One build at a time. Studio's builds, a cron site-build and a hand-started one share one lock.

Failures keep the last good site. A failed build keeps the previous site and is tried again on the next publish.

Bounded. A build has a deadline (CLOUDHAL_SITE_BUILD_TIMEOUT, 30 minutes by default). Stopping Studio during a build ends it within 5 seconds, with everything it started, and records it as stopped.

Every build is recorded in the site's Activity as "Build public site", with its duration, snapshot and output on failure. The site's overview shows a new "Public site build" card with the same details, and what visitors see now from /data/site/current.json, which site-build writes after each swap, so builds from cron or by hand show there too. The failure's output is shown only to roles with audit:read. CLOUDHAL_SITE_BUILD=off turns both off for sites built elsewhere, and a plain cloudhal studio keeps it off. For other integrations, ScheduledTickOptions.onReleasePublished (core-ts) reports releases that went live, ReleaseServiceOptions.onReleasePublished (and the API's SchedulesDeps.onReleasePublished) reports a release published now, openLocalStore takes onPublished, and GET /api/sites/:id/site-build reports the queue, the last build and what is served.

Corrections to the machine-drafted translations of collections, typed fields, listings, the OAuth consent screen, Connected agents, the setup-link sign-up text and the site status pages (#112), in all 18 non-English languages. The fixes cover changed meaning, security wording that had softened, mixed terms and mixed register. Examples: Indonesian said "not yet verified" for a self-registered agent, Polish dropped "you" from the loopback warning, and Japanese and Korean lost "never" in "never beyond your role". Korean used a formal register in the new screens while the rest of Studio uses its polite-informal one. Nothing else changes, and the languages remain AI drafts awaiting review by people who speak them.

cloudhal build --published (RFC-0043 §1.10) builds the published snapshot only, never the latest snapshot or the drafts. When nothing is published yet, it writes the not-published status page as the whole output instead, in the site's default language: index.html and 404.html, a robots.txt that disallows everything, a _headers file with no-store and noindex, and a .cloudhal-status marker. The Docker image's site-build now passes the flag, and the compose file's Caddyfile answers every path except robots.txt with that page, status 503 and Retry-After: 3600 while the marker exists. The image also runs site-build once in the background when Studio starts, so a fresh self-hosted site no longer serves drafts before its first publish, and a volume upgraded from 0.7.1 or older switches on its first start. cloudhal build without the flag is unchanged.

Upgrade
npm install @cloudhal/[email protected] @cloudhal/[email protected] @cloudhal/[email protected] @cloudhal/[email protected]
npx cloudhal deploy
Docs: https://cloudhal.dev/docs/start/installation#upgrading

Cloudhal 0.7.1

All @cloudhal/* packages and create-cloudhal at 0.7.1.

... (truncated)

Changelog

Sourced from @cloudhal/astro-renderer's changelog.

0.7.3

Patch Changes

403043b: Turkish: the strings added since the last review (the OAuth consent screen, Connected agents, the setup-link sign-up text, the Ended badge, the Build chat playground hint and the site status pages, #112) are reviewed and approved by the owner. 22 of 93 change: Connected agents says an agent "never" goes beyond your role again ("senin rolünü asla aşmaz"), "revoke" is "iptal et" as everywhere else, "operator" is "işletmeci" so it is not read as the Yönetici role, the setup-link text names the Sahip role, the consent title needs no suffix on the app's name, the invite page says "Çıkış yap" like its button, and the maintenance page says "Tahmini dönüş: {time}" and "Sabrınız için teşekkür ederiz".

Updated dependencies [5cb0a5d]

@cloudhal/core-ts@0.7.3

@cloudhal/comments@0.7.3

@cloudhal/analytics@0.7.3

@cloudhal/core-contracts@0.7.3

@cloudhal/storage@0.7.3

0.7.2

Patch Changes

6de8d67: Corrections to the machine-drafted translations of collections, typed fields, listings, the OAuth consent screen, Connected agents, the setup-link sign-up text and the site status pages (#112), in all 18 non-English languages. The fixes cover changed meaning, security wording that had softened, mixed terms and mixed register. Examples: Indonesian said "not yet verified" for a self-registered agent, Polish dropped "you" from the loopback warning, and Japanese and Korean lost "never" in "never beyond your role". Korean used a formal register in the new screens while the rest of Studio uses its polite-informal one. Nothing else changes, and the languages remain AI drafts awaiting review by people who speak them.

Updated dependencies [060a9c8]

@cloudhal/core-ts@0.7.2

@cloudhal/comments@0.7.2

@cloudhal/analytics@0.7.2

@cloudhal/core-contracts@0.7.2

@cloudhal/storage@0.7.2

0.7.1

Patch Changes

24fe76b: Security fixes from the CodeQL backlog on main.

Prototype pollution. A2UI updateDataModel paths (@cloudhal/core-ts/interop) that name __proto__, constructor or prototype at any depth are now refused with an InteropError instead of being skipped, step into arrays by index only, and write own properties only; an input whose component id is one of those keys gets the data key <id>-value. Surface pointers the page writes through (an input's value/checked, a Scrolly's step, a Button action's path) may not name those keys (a checkSurface issue); read bindings still may. The Build eval's sample inputs never write through them, and set_chrome and update_entry's fields merge patch refuse them as keys. RESERVED_KEYS and isReservedKey are new in @cloudhal/core-ts/names.

Plain text from HTML. htmlText (meta and feed descriptions, JSON-LD, table-of-contents labels) is plain text: <script> in markdown is the text <script>, as before, and every place it goes escapes it (now tested sink by sink). Tags are dropped with a linear scan, and entities are decoded once (&[#60](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/astro-renderer/issues/60); is the text &[#60](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/astro-renderer/issues/60);, no longer <).

Linear scans (AGENTS.md rule 13). The svg sniff of uploads (exponential on .

Updated dependencies [24fe76b]

@cloudhal/core-ts@0.7.1

@cloudhal/comments@0.7.1

@cloudhal/analytics@0.7.1

@cloudhal/core-contracts@0.7.1

@cloudhal/storage@0.7.1

0.7.0

Patch Changes

Updated dependencies [6057871]

Updated dependencies [d363160]

@cloudhal/storage@0.7.0

@cloudhal/core-ts@0.7.0

@cloudhal/analytics@0.7.0

@cloudhal/comments@0.7.0

... (truncated)

Commits

ce18da2 chore(release): version packages
403043b i18n(tr): review of the strings changed since the last Turkish review (#112)
21ae94c chore(release): version packages
6de8d67 fix(i18n): machine-draft QA pass and review packs (#112)
df800fb chore(release): version packages
02c4bc8 Merge pull request #188 from cloudhal-dev/chore/codeql-backlog-2
6a924b9 test(security): JSON-escape the JSON-LD probe; preview and proto id cases
c9296ae fix(security): review round for the CodeQL production alerts
6c30f57 chore(security): Actions permissions and test/script alerts (CodeQL)
24fe76b fix(security): prototype pollution, HTML text and ReDoS backlog (CodeQL)
Additional commits viewable in compare view

Updates @cloudhal/cli from 0.6.5 to 0.7.3

Release notes

Sourced from @cloudhal/cli's releases.

Cloudhal 0.7.3

All @cloudhal/* packages and create-cloudhal at 0.7.3.

Changes

asset_refs is scoped by site (RFC-0045 §2.5, rollout step 0), and an unchanged import no longer rebuilds it (#196).

An import, push or pull planned unchanged used to rebuild the site's asset_refs from rows read at plan time. An edit that committed in between could lose its new row, so the asset it started using could be deleted and showed as unused. The rebuild now runs only in a batch that also writes the node set.

The rebuild records only references to assets of the same site, and splits its INSERT so each statement stays below 90 KB (large sites could exceed D1's statement limit). Its statements count against the import's 1,000-statement cap.

Deleting an asset and the media library's "unused" filter look only at references from the asset's own site, so a foreign archive naming another site's asset no longer blocks its delete or hides it.

A publish that changes an asset now also purges the pages that show it through a typed image or richText field (RFC-0041), not only through covers, bodies and sections.

While a field rename runs, entries not rewritten yet still hold the old key. Both the rebuild and the purge planner now read those entries through the definition's migration.fromKey, as the renderer does. An archive exported mid-rename keeps those entries' rows, and an asset change purges their pages.

Turkish: the strings added since the last review (the OAuth consent screen, Connected agents, the setup-link sign-up text, the Ended badge, the Build chat playground hint and the site status pages, #112) are reviewed and approved by the owner. 22 of 93 change: Connected agents says an agent "never" goes beyond your role again ("senin rolünü asla aşmaz"), "revoke" is "iptal et" as everywhere else, "operator" is "işletmeci" so it is not read as the Yönetici role, the setup-link text names the Sahip role, the consent title needs no suffix on the app's name, the invite page says "Çıkış yap" like its button, and the maintenance page says "Tahmini dönüş: {time}" and "Sabrınız için teşekkür ederiz".

Upgrade
npm install @cloudhal/[email protected] @cloudhal/[email protected] @cloudhal/[email protected] @cloudhal/[email protected]
npx cloudhal deploy
Docs: https://cloudhal.dev/docs/start/installation#upgrading

Cloudhal 0.7.2

All @cloudhal/* packages and create-cloudhal at 0.7.2.

Changes

A self-hosted site rebuilds itself on publish (#150). With CLOUDHAL_SITE_BUILD=on, which is the Docker image's default, cloudhal studio runs the image's site-build in a child process after every publish: a publish in Studio or through MCP, an approval, a rollback, or a release that goes live (at its time or through "Publish now"). It also runs it once at start.

One build per burst. A burst of publishes builds once (3 seconds after the last one, at most a minute after the first).

One build at a time. Studio's builds, a cron site-build and a hand-started one share one lock.

Failures keep the last good site. A failed build keeps the previous site and is tried again on the next publish.

Bounded. A build has a deadline (CLOUDHAL_SITE_BUILD_TIMEOUT, 30 minutes by default). Stopping Studio during a build ends it within 5 seconds, with everything it started, and records it as stopped.

Every build is recorded in the site's Activity as "Build public site", with its duration, snapshot and output on failure. The site's overview shows a new "Public site build" card with the same details, and what visitors see now from /data/site/current.json, which site-build writes after each swap, so builds from cron or by hand show there too. The failure's output is shown only to roles with audit:read. CLOUDHAL_SITE_BUILD=off turns both off for sites built elsewhere, and a plain cloudhal studio keeps it off. For other integrations, ScheduledTickOptions.onReleasePublished (core-ts) reports releases that went live, ReleaseServiceOptions.onReleasePublished (and the API's SchedulesDeps.onReleasePublished) reports a release published now, openLocalStore takes onPublished, and GET /api/sites/:id/site-build reports the queue, the last build and what is served.

Corrections to the machine-drafted translations of collections, typed fields, listings, the OAuth consent screen, Connected agents, the setup-link sign-up text and the site status pages (#112), in all 18 non-English languages. The fixes cover changed meaning, security wording that had softened, mixed terms and mixed register. Examples: Indonesian said "not yet verified" for a self-registered agent, Polish dropped "you" from the loopback warning, and Japanese and Korean lost "never" in "never beyond your role". Korean used a formal register in the new screens while the rest of Studio uses its polite-informal one. Nothing else changes, and the languages remain AI drafts awaiting review by people who speak them.

cloudhal build --published (RFC-0043 §1.10) builds the published snapshot only, never the latest snapshot or the drafts. When nothing is published yet, it writes the not-published status page as the whole output instead, in the site's default language: index.html and 404.html, a robots.txt that disallows everything, a _headers file with no-store and noindex, and a .cloudhal-status marker. The Docker image's site-build now passes the flag, and the compose file's Caddyfile answers every path except robots.txt with that page, status 503 and Retry-After: 3600 while the marker exists. The image also runs site-build once in the background when Studio starts, so a fresh self-hosted site no longer serves drafts before its first publish, and a volume upgraded from 0.7.1 or older switches on its first start. cloudhal build without the flag is unchanged.

Upgrade
npm install @cloudhal/[email protected] @cloudhal/[email protected] @cloudhal/[email protected] @cloudhal/[email protected]
npx cloudhal deploy
Docs: https://cloudhal.dev/docs/start/installation#upgrading

Cloudhal 0.7.1

All @cloudhal/* packages and create-cloudhal at 0.7.1.

... (truncated)

Changelog

Sourced from @cloudhal/cli's changelog.

0.7.3

Patch Changes

403043b: Turkish: the strings added since the last review (the OAuth consent screen, Connected agents, the setup-link sign-up text, the Ended badge, the Build chat playground hint and the site status pages, #112) are reviewed and approved by the owner. 22 of 93 change: Connected agents says an agent "never" goes beyond your role again ("senin rolünü asla aşmaz"), "revoke" is "iptal et" as everywhere else, "operator" is "işletmeci" so it is not read as the Yönetici role, the setup-link text names the Sahip role, the consent title needs no suffix on the app's name, the invite page says "Çıkış yap" like its button, and the maintenance page says "Tahmini dönüş: {time}" and "Sabrınız için teşekkür ederiz".

Updated dependencies [5cb0a5d]

Updated dependencies [403043b]

@cloudhal/core-ts@0.7.3

@cloudhal/astro-renderer@0.7.3

@cloudhal/api@0.7.3

@cloudhal/cloudflare@0.7.3

@cloudhal/comments@0.7.3

@cloudhal/mcp-server@0.7.3

@cloudhal/agent-runtime@0.7.3

@cloudhal/analytics@0.7.3

@cloudhal/core-contracts@0.7.3

@cloudhal/schedules@0.7.3

@cloudhal/storage@0.7.3

0.7.2

Patch Changes

8526116: cloudhal build --published (RFC-0043 §1.10) builds the published snapshot only, never the latest snapshot or the drafts. When nothing is published yet, it writes the not-published status page as the whole output instead, in the site's default language: index.html and 404.html, a robots.txt that disallows everything, a _headers file with no-store and noindex, and a .cloudhal-status marker. The Docker image's site-build now passes the flag, and the compose file's Caddyfile answers every path except robots.txt with that page, status 503 and Retry-After: 3600 while the marker exists. The image also runs site-build once in the background when Studio starts, so a fresh self-hosted site no longer serves drafts before its first publish, and a volume upgraded from 0.7.1 or older switches on its first start. cloudhal build without the flag is unchanged.

6de8d67: Corrections to the machine-drafted translations of collections, typed fields, listings, the OAuth consent screen, Connected agents, the setup-link sign-up text and the site status pages (#112), in all 18 non-English languages. The fixes cover changed meaning, security wording that had softened, mixed terms and mixed register. Examples: Indonesian said "not yet verified" for a self-registered agent, Polish dropped "you" from the loopback warning, and Japanese and Korean lost "never" in "never beyond your role". Korean used a formal register in the new screens while the rest of Studio uses its polite-informal one. Nothing else changes, and the languages remain AI drafts awaiting review by people who speak them.

060a9c8: A self-hosted site rebuilds itself on publish (#150). With CLOUDHAL_SITE_BUILD=on, which is the Docker image's default, cloudhal studio runs the image's site-build in a child process after every publish: a publish in Studio or through MCP, an approval, a rollback, or a release that goes live (at its time or through "Publish now"). It also runs it once at start.

One build per burst. A burst of publishes builds once (3 seconds after the last one, at most a minute after the first).

One build at a time. Studio's builds, a cron site-build and a hand-started one share one lock.

Failures keep the last good site. A failed build keeps the previous site and is tried again on the next publish.

Bounded. A build has a deadline (CLOUDHAL_SITE_BUILD_TIMEOUT, 30 minutes by default). Stopping Studio during a build ends it within 5 seconds, with everything it started, and records it as stopped.

Every build is recorded in the site's Activity as "Build public site", with its duration, snapshot and output on failure. The site's overview shows a new "Public site build" card with the same details, and what visitors see now from /data/site/current.json, which site-build writes after each swap, so builds from cron or by hand show there too. The failure's output is shown only to roles with audit:read. CLOUDHAL_SITE_BUILD=off turns both off for sites built elsewhere, and a plain cloudhal studio keeps it off. For other integrations, ScheduledTickOptions.onReleasePublished (core-ts) reports releases that went live, ReleaseServiceOptions.onReleasePublished (and the API's SchedulesDeps.onReleasePublished) reports a release published now, openLocalStore takes onPublished, and GET /api/sites/:id/site-build reports the queue, the last build and what is served.

Updated dependencies [6de8d67]

Updated dependencies [060a9c8]

@cloudhal/astro-renderer@0.7.2

@cloudhal/api@0.7.2

@cloudhal/core-ts@0.7.2

@cloudhal/mcp-server@0.7.2

@cloudhal/cloudflare@0.7.2

@cloudhal/comments@0.7.2

@cloudhal/agent-runtime@0.7.2

@cloudhal/analytics@0.7.2

@cloudhal/core-contracts@0.7.2

@cloudhal/schedules@0.7.2

@cloudhal/storage@0.7.2

0.7.1

Patch Changes

... (truncated)

Commits

ce18da2 chore(release): version packages
21ae94c chore(release): version packages
3198ba0 fix(cli): capture the live build while streaming (#150)
055765e fix(cli): keep the publish swap whole and polling alive (#150)
77e2948 fix(cli): review round for site rebuild on publish (#150)
060a9c8 feat(cli): rebuild the self-hosted site on publish (#150)
d3e22eb fix(docker): never-latest tests, older CLIs, a site build at start (RFC-0043 ...
8526116 feat(cli): cloudhal build --published and the static not-published page (RFC-...
df800fb chore(release): version packages
02c4bc8 Merge pull request #188 from cloudhal-dev/chore/codeql-backlog-2
Additional commits viewable in compare view

Updates @cloudhal/core-ts from 0.6.5 to 0.7.3

Release notes

Sourced from @cloudhal/core-ts's releases.

Cloudhal 0.7.3

All @cloudhal/* packages and create-cloudhal at 0.7.3.

Changes

asset_refs is scoped by site (RFC-0045 §2.5, rollout step 0), and an unchanged import no longer rebuilds it (#196).

An import, push or pull planned unchanged used to rebuild the site's asset_refs from rows read at plan time. An edit that committed in between could lose its new row, so the asset it started using could be deleted and showed as unused. The rebuild now runs only in a batch that also writes the node set.

The rebuild records only references to assets of the same site, and splits its INSERT so each statement stays below 90 KB (large sites could exceed D1's statement limit). Its statements count against the import's 1,000-statement cap.

Deleting an asset and the media library's "unused" filter look only at references from the asset's own site, so a foreign archive naming another site's asset no longer blocks its delete or hides it.

A publish that changes an asset now also purges the pages that show it through a typed image or richText field (RFC-0041), not only through covers, bodies and sections.

While a field rename runs, entries not rewritten yet still hold the old key. Both the rebuild and the purge planner now read those entries through the definition's migration.fromKey, as the renderer does. An archive exported mid-rename keeps those entries' rows, and an asset change purges their pages.

Turkish: the strings added since the last review (the OAuth consent screen, Connected agents, the setup-link sign-up text, the Ended badge, the Build chat playground hint and the site status pages, #112) are reviewed and approved by the owner. 22 of 93 change: Connected agents says an agent "never" goes beyond your role again ("senin rolünü asla aşmaz"), "revoke" is "iptal et" as everywhere else, "operator" is "işletmeci" so it is not read as the Yönetici role, the setup-link text names the Sahip role, the consent title needs no suffix on the app's name, the invite page says "Çıkış yap" like its button, and the maintenance page says "Tahmini dönüş: {time}" and "Sabrınız için teşekkür ederiz".

Upgrade
npm install @cloudhal/[email protected] @cloudhal/[email protected] @cloudhal/[email protected] @cloudhal/[email protected]
npx cloudhal deploy
Docs: https://cloudhal.dev/docs/start/installation#upgrading

Cloudhal 0.7.2

All @cloudhal/* packages and create-cloudhal at 0.7.2.

Changes

A self-hosted site rebuilds itself on publish (#150). With CLOUDHAL_SITE_BUILD=on, which is the Docker image's default, cloudhal studio runs the image's site-build in a child process after every publish: a publish in Studio or through MCP, an approval, a rollback, or a release that goes live (at its time or through "Publish now"). It also runs it once at start.

One build per burst. A burst of publishes builds once (3 seconds after the last one, at most a minute after the first).

One build at a time. Studio's builds, a cron site-build and a hand-started one share one lock.

Failures keep the last good site. A failed build keeps the previous site and is tried again on the next publish.

Bounded. A build has a deadline (CLOUDHAL_SITE_BUILD_TIMEOUT, 30 minutes by default). Stopping Studio during a build ends it within 5 seconds, with everything it started, and records it as stopped.

Every build is recorded in the site's Activity as "Build public site", with its duration, snapshot and output on failure. The site's overview shows a new "Public site build" card with the same details, and what visitors see now from /data/site/current.json, which site-build writes after each swap, so builds from cron or by hand show there too. The failure's output is shown only to roles with audit:read. CLOUDHAL_SITE_BUILD=off turns both off for sites built elsewhere, and a plain cloudhal studio keeps it off. For other integrations, ScheduledTickOptions.onReleasePublished (core-ts) reports releases that went live, ReleaseServiceOptions.onReleasePublished (and the API's SchedulesDeps.onReleasePublished) reports a release published now, openLocalStore takes onPublished, and GET /api/sites/:id/site-build reports the queue, the last build and what is served.

Corrections to the machine-drafted translations of collections, typed fields, listings, the OAuth consent screen, Connected agents, the setup-link sign-up text and the site status pages (#112), in all 18 non-English languages. The fixes cover changed meaning, security wording that had softened, mixed terms and mixed register. Examples: Indonesian said "not yet verified" for a self-registered agent, Polish dropped "you" from the loopback warning, and Japanese and Korean lost "never" in "never beyond your role". Korean used a formal register in the new screens while the rest of Studio uses its polite-informal one. Nothing else changes, and the languages remain AI drafts awaiting review by people who speak them.

cloudhal build --published (RFC-0043 §1.10) builds the published snapshot only, never the latest snapshot or the drafts. When nothing is published yet, it writes the not-published status page as the whole output instead, in the site's default language: index.html and 404.html, a robots.txt that disallows everything, a _headers file with no-store and noindex, and a .cloudhal-status marker. The Docker image's site-build now passes the flag, and the compose file's Caddyfile answers every path except robots.txt with that page, status 503 and Retry-After: 3600 while the marker exists. The image also runs site-build once in the background when Studio starts, so a fresh self-hosted site no longer serves drafts before its first publish, and a volume upgraded from 0.7.1 or older switches on its first start. cloudhal build without the flag is unchanged.

Upgrade
npm install @cloudhal/[email protected] @cloudhal/[email protected] @cloudhal/[email protected] @cloudhal/[email protected]
npx cloudhal deploy
Docs: https://cloudhal.dev/docs/start/installation#upgrading

Cloudhal 0.7.1

All @cloudhal/* packages and create-cloudhal at 0.7.1.

... (truncated)

Changelog

Sourced from @cloudhal/core-ts's changelog.

0.7.3

Patch Changes

5cb0a5d: asset_refs is scoped by site (RFC-0045 §2.5, rollout step 0), and an unchanged import no longer rebuilds it (#196).

An import, push or pull planned unchanged used to rebuild the site's asset_refs from rows read at plan time. An edit that committed in between could lose its new row, so the asset it started using could be deleted and showed as unused. The rebuild now runs only in a batch that also writes the node set.

The rebuild records only references to assets of the same site, and splits its INSERT so each statement stays below 90 KB (large sites could exceed D1's statement limit). Its statements count against the import's 1,000-statement cap.

Deleting an asset and the media library's "unused" filter look only at references from the asset's own site, so a foreign archive naming another site's asset no longer blocks its delete or hides it.

A publish that changes an asset now also purges the pages that show it through a typed image or richText field (RFC-0041), not only through covers, bodies and sections.

While a field rename runs, entries not rewritten yet still hold the old key. Both the rebuild and the purge planner now read those entries through the definition's migration.fromKey, as the renderer does. An archive exported mid-rename keeps those entries' rows, and an asset change purges their pages.

@cloudhal/core-contracts@0.7.3

@cloudhal/schedules@0.7.3

@cloudhal/storage@0.7.3

0.7.2

Patch Changes

060a9c8: A self-hosted site rebuilds itself on publish (#150). With CLOUDHAL_SITE_BUILD=on, which is the Docker image's default, cloudhal studio runs the image's site-build in a child process after every publish: a publish in Studio or through MCP, an approval, a rollback, or a release that goes live (at its time or through "Publish now"). It also runs it once at start.

One build per burst. A burst of publishes builds once (3 seconds after the last one, at most a minute after the first).

One build at a time. Studio's builds, a cron site-build and a hand-started one share one lock.

Failures keep the last good site. A failed build keeps the previous site and is tried again on the next publish.

Bounded. A build has a deadline (CLOUDHAL_SITE_BUILD_TIMEOUT, 30 minutes by default). Stopping Studio during a build ends it within 5 seconds, with everything it started, and records it as stopped.

Every build is recorded in the site's Activity as "Build public site", with its duration, snapshot and output on failure. The site's overview shows a new "Public site build" card with the same details, and what visitors see now from /data/site/current.json, which site-build writes after each swap, so builds from cron or by hand show there too. The failure's output is shown only to roles with audit:read. CLOUDHAL_SITE_BUILD=off turns both off for sites built elsewhere, and a plain cloudhal studio keeps it off. For other integrations, ScheduledTickOptions.onReleasePublished (core-ts) reports releases that went live, ReleaseServiceOptions.onReleasePublished (and the API's SchedulesDeps.onReleasePublished) reports a release published now, openLocalStore takes onPublished, and GET /api/sites/:id/site-build reports the queue, the last build and what is served.

@cloudhal/core-contracts@0.7.2

@cloudhal/schedules@0.7.2

@cloudhal/storage@0.7.2

0.7.1

Patch Changes

24fe76b: Security fixes from the CodeQL backlog on main.

Prototype pollution. A2UI updateDataModel paths (@cloudhal/core-ts/interop) that name __proto__, constructor or prototype at any depth are now refused with an InteropError instead of being skipped, step into arrays by index only, and write own properties only; an input whose component id is one of those keys gets the data key <id>-value. Surface pointers the page writes through (an input's value/checked, a Scrolly's step, a Button action's path) may not name those keys (a checkSurface issue); read bindings still may. The Build eval's sample inputs never write through them, and set_chrome and update_entry's fields merge patch refuse them as keys. RESERVED_KEYS and isReservedKey are new in @cloudhal/core-ts/names.

Plain text from HTML. htmlText (meta and feed descriptions, JSON-LD, table-of-contents labels) is plain text: <script> in markdown is the text <script>, as before, and every place it goes escapes it (now tested sink by sink). Tags are dropped with a linear scan, and entities are decoded once (&[#60](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/core-ts/issues/60); is the text &[#60](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/core-ts/issues/60);, no longer <).

Linear scans (AGENTS.md rule 13). The svg sniff of uploads (exponential on .

@cloudhal/core-contracts@0.7.1

@cloudhal/schedules@0.7.1

@cloudhal/storage@0.7.1

0.7.0

Patch Changes

d363160: Remote MCP clients can now register themselves (RFC-0044 Phase 3a, ADR-0045). Clients that name an HTTPS Client ID Metadata Document as their client_id (Claude Code, Codex, VS Code) are accepted through @better-auth/cimd, fetched with the media import's SSRF-safe transport (pinned on Node, DoH-checked on Workers; https only, public addresses only, no redirects, 5 KB, 5 s). Clients without one (Cursor) use dynamic client registration at /api/auth/oauth2/register: public clients only, rate-limited per address and per day, capped at 5,000, and pruned by the scheduler after 30 unused days. Document clients are fetched at most hourly per client, with budgets in Cloudhal's own counters that never lock out stored clients, a cap of 5,000 that evicts unused clients (the well-known clients' hosts are exempt), pruning after three hours unused, and a failed refetch that refuses the client; migration 0032_oauth_client_kind_index indexes them. Redirect URIs must be https, loopback http (any port) or a native app's private-use scheme (cursor, vscode, reverse-domain, CLOUDHAL_MCP_REDIRECT_SCHEMES), and the client host list applies at every authorization. With DCR off, the clients it registered earlier cannot start new authorizations. The consent screen shows client names plain and short, a document client's host first, and marks self-registered clients as unverified. CLOUDHAL_MCP_CIMD=off, CLOUDHAL_MCP_DCR=off, CLOUDHAL_MCP_CLIENT_HOSTS and CLOUDHAL_MCP_REDIRECT_SCHEMES control it on both runtimes, and the Docker compose file passes them through. The Phase 2 server-side test client (OauthServer.createClient) is removed. set_embargo through an OAuth connection now files the gate for a person's approval instead of leaving it unapplied, and the request is notified while it waits. safeFetch results carry the response headers.

Updated dependencies [6057871]

... (truncated)

Commits

ce18da2 chore(release): version packages
1eda0f9 fix(core-ts): read field assets through a running rename's fromKey (#196 review)
5cb0a5d fix(core-ts): scope asset_refs by site and skip rebuilds on unchanged imports...
21ae94c chore(release): version packages
77e2948 fix(cli): review round for site rebuild on publish (#150)
060a9c8 feat(cli): rebuild the self-hosted site on publish (#150)
df800fb chore(release): version packages
6a924b9 test(security): JSON-escape the JSON-LD probe; preview and proto id cases
6f70ae0 refactor(core-ts): keep fromA2ui within the size baseline
c9296ae fix(security): review round for the CodeQL production alerts
Additional commits viewable in compare view

Updates @cloudhal/cloudflare from 0.6.5 to 0.7.3

Release notes

Sourced from @cloudhal/cloudflare's releases.

Cloudhal 0.7.3

All @cloudhal/* packages and create-cloudhal at 0.7.3.

Changes

asset_refs is scoped by site (RFC-0045 §2.5, rollout step 0), and an unchanged import no longer rebuilds it (#196).

An import, push or pull planned unchanged used to rebuild the site's asset_refs from rows read at plan time. An edit that committed in between could lose its new row, so the asset it started using could be deleted and showed as unused. The rebuild now runs only in a batch that also writes the node set.

The rebuild records only references to assets of the same site, and splits its INSERT so each statement stays below 90 KB (large sites could exceed D1's statement limit). Its statements count against the import's 1,000-statement cap.

Deleting an asset and the media library's "unused" filter look only at references from the asset's own site, so a foreign archive naming another site's asset no longer blocks its delete or hides it.

A publish that changes an asset now also purges the pages that show it through a typed image or richText field (RFC-0041), not only through covers, bodies and sections.

While a field rename runs, entries not rewritten yet still hold the old key. Both the rebuild and the purge planner now read those entries through the definition's migration.fromKey, as the renderer does. An archive exported mid-rename keeps those entries' rows, and an asset change purges their pages.

Turkish: the strings added since the last review (the OAuth consent screen, Connected agents, the setup-link sign-up text, the Ended badge, the Build chat playground hint and the site status pages, #112) are reviewed and approved by the owner. 22 of 93 change: Connected agents says an agent "never" goes beyond your role again ("senin rolünü asla aşmaz"), "revoke" is "iptal et" as everywhere else, "operator" is "işletmeci" so it is not read as the Yönetici role, the setup-link text names the Sahip role, the consent title needs no suffix on the app's name, the invite page says "Çıkış yap" like its button, and the maintenance page says "Tahmini dönüş: {time}" and "Sabrınız için teşekkür ederiz".

Upgrade
npm install @cloudhal/[email protected] @cloudhal/[email protected] @cloudhal/[email protected] @cloudhal/[email protected]
npx cloudhal deploy
Docs: https://cloudhal.dev/docs/start/installation#upgrading

Cloudhal 0.7.2

All @cloudhal/* packages and create-cloudhal at 0.7.2.

Changes

A self-hosted site rebuilds itself on publish (#150). With CLOUDHAL_SITE_BUILD=on, which is the Docker image's default, cloudhal studio runs the image's site-build in a child process after every publish: a publish in Studio or through MCP, an approval, a rollback, or a release that goes live (at its time or through "Publish now"). It also runs it once at start.

One build per burst. A burst of publishes builds once (3 seconds after the last one, at most a minute after the first).

One build at a time. Studio's builds, a cron site-build and a hand-started one share one lock.

Failures keep the last good site. A failed build keeps the previous site and is tried again on the next publish.

Bounded. A build has a deadline (CLOUDHAL_SITE_BUILD_TIMEOUT, 30 minutes by default). Stopping Studio during a build ends it within 5 seconds, with everything it started, and records it as stopped.

Every build is recorded in the site's Activity as "Build public site", with its duration, snapshot and output on failure. The site's overview shows a new "Public site build" card with the same details, and what visitors see now from /data/site/current.json, which site-build writes after each swap, so builds from cron or by hand show there too. The failure's output is shown only to roles with audit:read. CLOUDHAL_SITE_BUILD=off turns both off for sites built elsewhere, and a plain cloudhal studio keeps it off. For other integrations, ScheduledTickOptions.onReleasePublished (core-ts) reports releases that went live, ReleaseServiceOptions.onReleasePublished (and the API's SchedulesDeps.onReleasePublished) reports a release published now, openLocalStore takes onPublished, and GET /api/sites/:id/site-build reports the queue, the last build and what is served.

Corrections to the machine-drafted translations of collections, typed fields, listings, the OAuth consent screen, Connected agents, the setup-link sign-up text and the site status pages (#112), in all 18 non-English languages. The fixes cover changed meaning, security wording that had softened, mixed terms and mixed register. Examples: Indonesian said "not yet verified" for a self-registered agent, Polish dropped "you" from the loopback warning, and Japanese and Korean lost "never" in "never beyond your role". Korean used a formal register in the new screens while the rest of Studio uses its polite-informal one. Nothing else changes, and the languages remain AI drafts awaiting review by people who speak them.

cloudhal build --published (RFC-0043 §1.10) builds the published snapshot only, never the latest snapshot or the drafts. When nothing is published yet, it writes the not-published status page as the whole output instead, in the site's default language: index.html and 404.html, a robots.txt that disallows everything, a _headers file with no-store and noindex, and a .cloudhal-status marker. The Docker image's site-build now passes the flag, and the compose file's Caddyfile answers every path except robots.txt with that page, status 503 and Retry-After: 3600 while the marker exists. The image also runs site-build once in the background when Studio starts, so a fresh self-hosted site no longer serves drafts before its first publish, and a volume upgraded from 0.7.1 or older switches on its first start. cloudhal build without the flag is unchanged.

Upgrade
npm install @cloudhal/[email protected] @cloudhal/[email protected] @cloudhal/[email protected] @cloudhal/[email protected]
npx cloudhal deploy
Docs: https://cloudhal.dev/docs/start/installation#upgrading

Cloudhal 0.7.1

All @cloudhal/* packages and create-cloudhal at 0.7.1.
...
Description has been truncated

Bumps the cloudhal group with 12 updates: | Package | From | To | | --- | --- | --- | | [@cloudhal/astro-renderer](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/astro-renderer) | `0.6.5` | `0.7.3` | | [@cloudhal/cli](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/cli) | `0.6.5` | `0.7.3` | | [@cloudhal/core-ts](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/core-ts) | `0.6.5` | `0.7.3` | | [@cloudhal/cloudflare](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/cloudflare) | `0.6.5` | `0.7.3` | | [@cloudhal/agent-runtime](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/agent-runtime) | `0.6.5` | `0.7.3` | | [@cloudhal/analytics](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/analytics) | `0.6.5` | `0.7.3` | | [@cloudhal/api](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/api) | `0.6.5` | `0.7.3` | | [@cloudhal/comments](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/comments) | `0.6.5` | `0.7.3` | | [@cloudhal/core-contracts](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/core-contracts) | `0.6.5` | `0.7.3` | | [@cloudhal/mcp-server](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/mcp-server) | `0.6.5` | `0.7.3` | | [@cloudhal/schedules](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/schedules) | `0.6.5` | `0.7.3` | | [@cloudhal/storage](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/storage) | `0.6.5` | `0.7.3` | Updates `@cloudhal/astro-renderer` from 0.6.5 to 0.7.3 - [Release notes](https://github.com/cloudhal-dev/cloudhal/releases) - [Changelog](https://github.com/cloudhal-dev/cloudhal/blob/main/packages/astro-renderer/CHANGELOG.md) - [Commits](https://github.com/cloudhal-dev/cloudhal/commits/v0.7.3/packages/astro-renderer) Updates `@cloudhal/cli` from 0.6.5 to 0.7.3 - [Release notes](https://github.com/cloudhal-dev/cloudhal/releases) - [Changelog](https://github.com/cloudhal-dev/cloudhal/blob/main/packages/cli/CHANGELOG.md) - [Commits](https://github.com/cloudhal-dev/cloudhal/commits/v0.7.3/packages/cli) Updates `@cloudhal/core-ts` from 0.6.5 to 0.7.3 - [Release notes](https://github.com/cloudhal-dev/cloudhal/releases) - [Changelog](https://github.com/cloudhal-dev/cloudhal/blob/main/packages/core-ts/CHANGELOG.md) - [Commits](https://github.com/cloudhal-dev/cloudhal/commits/v0.7.3/packages/core-ts) Updates `@cloudhal/cloudflare` from 0.6.5 to 0.7.3 - [Release notes](https://github.com/cloudhal-dev/cloudhal/releases) - [Changelog](https://github.com/cloudhal-dev/cloudhal/blob/main/packages/cloudflare/CHANGELOG.md) - [Commits](https://github.com/cloudhal-dev/cloudhal/commits/v0.7.3/packages/cloudflare) Updates `@cloudhal/agent-runtime` from 0.6.5 to 0.7.3 - [Release notes](https://github.com/cloudhal-dev/cloudhal/releases) - [Changelog](https://github.com/cloudhal-dev/cloudhal/blob/main/packages/agent-runtime/CHANGELOG.md) - [Commits](https://github.com/cloudhal-dev/cloudhal/commits/v0.7.3/packages/agent-runtime) Updates `@cloudhal/analytics` from 0.6.5 to 0.7.3 - [Release notes](https://github.com/cloudhal-dev/cloudhal/releases) - [Changelog](https://github.com/cloudhal-dev/cloudhal/blob/main/packages/analytics/CHANGELOG.md) - [Commits](https://github.com/cloudhal-dev/cloudhal/commits/v0.7.3/packages/analytics) Updates `@cloudhal/api` from 0.6.5 to 0.7.3 - [Release notes](https://github.com/cloudhal-dev/cloudhal/releases) - [Changelog](https://github.com/cloudhal-dev/cloudhal/blob/main/packages/api/CHANGELOG.md) - [Commits](https://github.com/cloudhal-dev/cloudhal/commits/v0.7.3/packages/api) Updates `@cloudhal/comments` from 0.6.5 to 0.7.3 - [Release notes](https://github.com/cloudhal-dev/cloudhal/releases) - [Changelog](https://github.com/cloudhal-dev/cloudhal/blob/main/packages/comments/CHANGELOG.md) - [Commits](https://github.com/cloudhal-dev/cloudhal/commits/v0.7.3/packages/comments) Updates `@cloudhal/core-contracts` from 0.6.5 to 0.7.3 - [Release notes](https://github.com/cloudhal-dev/cloudhal/releases) - [Changelog](https://github.com/cloudhal-dev/cloudhal/blob/main/packages/core-contracts/CHANGELOG.md) - [Commits](https://github.com/cloudhal-dev/cloudhal/commits/v0.7.3/packages/core-contracts) Updates `@cloudhal/mcp-server` from 0.6.5 to 0.7.3 - [Release notes](https://github.com/cloudhal-dev/cloudhal/releases) - [Changelog](https://github.com/cloudhal-dev/cloudhal/blob/main/packages/mcp-server/CHANGELOG.md) - [Commits](https://github.com/cloudhal-dev/cloudhal/commits/v0.7.3/packages/mcp-server) Updates `@cloudhal/schedules` from 0.6.5 to 0.7.3 - [Release notes](https://github.com/cloudhal-dev/cloudhal/releases) - [Changelog](https://github.com/cloudhal-dev/cloudhal/blob/main/packages/schedules/CHANGELOG.md) - [Commits](https://github.com/cloudhal-dev/cloudhal/commits/v0.7.3/packages/schedules) Updates `@cloudhal/storage` from 0.6.5 to 0.7.3 - [Release notes](https://github.com/cloudhal-dev/cloudhal/releases) - [Changelog](https://github.com/cloudhal-dev/cloudhal/blob/main/packages/storage/CHANGELOG.md) - [Commits](https://github.com/cloudhal-dev/cloudhal/commits/v0.7.3/packages/storage) --- updated-dependencies: - dependency-name: "@cloudhal/astro-renderer" dependency-version: 0.7.3 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: cloudhal - dependency-name: "@cloudhal/cli" dependency-version: 0.7.3 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: cloudhal - dependency-name: "@cloudhal/core-ts" dependency-version: 0.7.3 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: cloudhal - dependency-name: "@cloudhal/cloudflare" dependency-version: 0.7.3 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: cloudhal - dependency-name: "@cloudhal/agent-runtime" dependency-version: 0.7.3 dependency-type: indirect update-type: version-update:semver-minor dependency-group: cloudhal - dependency-name: "@cloudhal/analytics" dependency-version: 0.7.3 dependency-type: indirect update-type: version-update:semver-minor dependency-group: cloudhal - dependency-name: "@cloudhal/api" dependency-version: 0.7.3 dependency-type: indirect update-type: version-update:semver-minor dependency-group: cloudhal - dependency-name: "@cloudhal/comments" dependency-version: 0.7.3 dependency-type: indirect update-type: version-update:semver-minor dependency-group: cloudhal - dependency-name: "@cloudhal/core-contracts" dependency-version: 0.7.3 dependency-type: indirect update-type: version-update:semver-minor dependency-group: cloudhal - dependency-name: "@cloudhal/mcp-server" dependency-version: 0.7.3 dependency-type: indirect update-type: version-update:semver-minor dependency-group: cloudhal - dependency-name: "@cloudhal/schedules" dependency-version: 0.7.3 dependency-type: indirect update-type: version-update:semver-minor dependency-group: cloudhal - dependency-name: "@cloudhal/storage" dependency-version: 0.7.3 dependency-type: indirect update-type: version-update:semver-minor dependency-group: cloudhal ... Signed-off-by: dependabot[bot] <[email protected]>

cloudflare-workers-and-pages · 2026-11-11T03:08:53Z

Deploying with Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
✅ Deployment successful! View logs	cloudhal-com-site	`365172a`	Nov 11 2026, 03:08 AM

dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 11, 2026

Navigation Menu

Repository navigation

chore: Bump the cloudhal group with 12 updates - #27

chore: Bump the cloudhal group with 12 updates#27
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/cloudhal-13e48a7be2

dependabot Bot commented on behalf of github Nov 11, 2026 •

edited

Loading

Uh oh!

cloudflare-workers-and-pages Bot commented Nov 11, 2026 •

edited

Loading

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

dependabot Bot commented on behalf of github Nov 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Cloudhal 0.7.3

Changes

Upgrade

Cloudhal 0.7.2

Changes

Upgrade

Cloudhal 0.7.1

0.7.3

Patch Changes

0.7.2

Patch Changes

0.7.1

Patch Changes

0.7.0

Patch Changes

Cloudhal 0.7.3

Changes

Upgrade

Cloudhal 0.7.2

Changes

Upgrade

Cloudhal 0.7.1

0.7.3

Patch Changes

0.7.2

Patch Changes

0.7.1

Patch Changes

Cloudhal 0.7.3

Changes

Upgrade

Cloudhal 0.7.2

Changes

Upgrade

Cloudhal 0.7.1

0.7.3

Patch Changes

0.7.2

Patch Changes

0.7.1

Patch Changes

0.7.0

Patch Changes

Cloudhal 0.7.3

Changes

Upgrade

Cloudhal 0.7.2

Changes

Upgrade

Cloudhal 0.7.1

Uh oh!

cloudflare-workers-and-pages Bot commented Nov 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Deploying with Cloudflare Workers

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

dependabot Bot commented on behalf of github Nov 11, 2026 •

edited

Loading

cloudflare-workers-and-pages Bot commented Nov 11, 2026 •

edited

Loading